VT-d: fix assertion fault in pci passthrough code
authorKeir Fraser <keir.fraser@citrix.com>
Mon, 13 Jul 2009 10:52:49 +0000 (11:52 +0100)
committerKeir Fraser <keir.fraser@citrix.com>
Mon, 13 Jul 2009 10:52:49 +0000 (11:52 +0100)
commitfbaf0db4fc12f64072d81576de944e87f23714c7
tree0098073e36bd9350ac8f5bf110eeaceb660dfc1e
parente1b075eaf13283dd695d33fb53d63fabd9067d4f
VT-d: fix assertion fault in pci passthrough code

Remove ASSERT(spin_is_locked(&pcidevs_lock)) in
pci_get_pdev_by_domain() to allow caller the flexibility to not hold
the lock if it does not care if the device is hot removed between the
time it got the pdev and the time it is used to get the corresponding
vt-d engine.  In the new RHSA use case, we just wanted to get the vt-d
engine of any device passthrough in the domain. Also, rename RHSA
field "domain" to "proximity domain" to avoid overloading the term
"domain" in virtualization context.

Signed-off-by: Allen Kay <allen.m.kay@intel.com>
xen/drivers/passthrough/pci.c
xen/drivers/passthrough/vtd/dmar.c
xen/drivers/passthrough/vtd/dmar.h
xen/drivers/passthrough/vtd/iommu.c
xen/include/xen/acpi.h